System and method for providing rate control in a network environment

ABSTRACT

A method is provided in one example embodiment and includes identifying a bandwidth parameter associated with a network link. The method includes evaluating a bandwidth request associated with user equipment, the bandwidth request is associated with a session, which involves the user equipment and which implicates the network link. The bandwidth request can be modified based on the bandwidth parameter that was identified. In more detailed embodiments, one or more header extensions in one or more packets are evaluated in order to assist in identifying the bandwidth parameter. The one or more header extensions can include a selected one of packet sequence numbers, an average packet transmission rate, an average packet receiving rate, and a packet reception error rate. In other examples, modifying the bandwidth request can include downgrading the bandwidth request to lower a bit rate based on the bandwidth parameter identified for the network link.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to providing rate control in a network environment.

BACKGROUND

Networking architectures have grown increasingly complex incommunication environments. For example, femto cells have gained recentnotoriety due to their capabilities. In general terms, femto cellsrepresent wireless access points that operate in licensed spectrum toconnect mobile devices to a mobile operator's network (e.g., usingbroadband connections). For a mobile operator, the femto cells offerimprovements to both coverage and capacity. For many service networkscenarios, bandwidth and/or resource allocation protocols can pose anumber of problems for end users and network operators. In otherscenarios, local Internet Protocol (IP) network access communicationscan have similar bandwidth allocation issues. For all of theaforementioned technologies (and for others), bandwidth managementpresents a significant challenge to network operators, device designers,and system administrators alike.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1 is a simplified block diagram of a communication system forproviding rate control in a network environment in accordance with oneembodiment of the present disclosure; and

FIGS. 2-4 are simplified flow diagrams illustrating potential operationsassociated with the communication system.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

A method is provided in one example embodiment and includes identifyinga bandwidth parameter associated with a network link. The method alsoincludes evaluating a bandwidth request associated with user equipment,the bandwidth request is associated with a session, which involves theuser equipment and which implicates the network link. The bandwidthrequest can be modified based on the bandwidth parameter that wasidentified. In more specific embodiments, one or more header extensionsin one or more packets are evaluated in order to assist in identifyingthe bandwidth parameter. The one or more header extensions can include aselected one of packet sequence numbers, an average packet transmissionrate, an average packet receiving rate, and a packet reception errorrate. In other examples, modifying the bandwidth request includesdowngrading the bandwidth request to lower a bit rate based on thebandwidth parameter identified for the network link. In still otherexamples, the bandwidth parameter associated with the network link canbe subsequently evaluated in order to reverse the downgrading of thebandwidth request.

EXAMPLE EMBODIMENTS

Turning to FIG. 1, FIG. 1 is a simplified block diagram of acommunication system 10 for managing rate controls for datatransmissions in one example implementation. FIG. 1 may include abackhaul network 12, user equipment (UE) 20, an Internet 22, a localInternet protocol (IP) network 28, a base station 30, and a networkelement 42. Base station 30 may include a base station switch 26, whichcan include a bandwidth sensing module 34 a, a memory element 36 a, anda processor 38 a. Similarly, network element 42 may include a bandwidthsensing module 34 b, a memory element 36 b, and a processor 38 b. FIG. 1may also include a packet gateway 40, a serving gateway 54, a mobilitymanagement entity (MME) 56, a media server #1 60, and a media server #250.

For purposes of illustrating certain example techniques of communicationsystem 10, it is important to understand the communications that may betraversing the network and which can be used to allocate bandwidth for agiven end user. In a wireless network (e.g., satellite, terrestrialcellular, femto, etc.), the dynamic nature of wireless channels cancause an inconsistency with that which can be accommodated by basestation 30 (or equivalently, by a femto base station, by a satelliteradio gateway, etc.). In specific regards to femto technology, femtocells allow licensed radios to be positioned at the end of a consumerbroadband line. As radio technology improves, consumer broadband canlimit the throughput of a femto cell. Typically, femto flows can bebroken out in the home in which established broadband bottlenecks do notapply.

Consider an example that is illustrative of some of the bandwidthproblems that may be encountered and resolved in communication system10. UE 20 may request a particular bit rate (e.g., data propagationspeed) associated with a bearer. For example, UE 20 may request a 1MB/second uplink bearer, which is simply not feasible. Packets wouldthen traverse the air interface, where a corresponding base stationwould simply drop these packets. In one sense, this is due to the lackof backpressure from (for example) a digital subscriber line (DSL)modem. Similarly, in a macro network environment, there could be amicrowave Ethernet system, which has a connection to a base station thatdetermines whether packets would be dropped at a certain interface(e.g., on a given port).

The femto use case in such a scenario is somewhat more manageablebecause protocols are terminated at base station 30. Further, specificmessages can be used (and further enhanced) to signal particularconditions, downgrade commands, termination activities, etc. Forexample, a particular service request can be downgraded for UE 20 usingappropriate messaging. This messaging is more complicated in the macronetwork because UE 20 typically sends his bearer request to MME 56, orto a serving general packet radio service (GPRS) support node (SGSN) inthe 3 G scenario, etc. and, therefore, that request would have to beintercepted before any downgrading occurred.

Communication system 10 can address these bandwidth issues (and others)in offering an automatic and adaptive rate control for one or morelinks. In one example implementation, base station 30 can be configuredto understand the bandwidth on its associated link with network element42. This could involve GPRS tunneling protocol (GTP) communications,real-time transport protocol (RTP) communications, or any other suitableprotocol (or probing mechanisms) in which bandwidth and delay can besensed for an associated link. In one example implementation, thissensing activity can be continuous, or at least periodic, such that thebandwidth sensing would occur at routine intervals. Bandwidth sensingmodules 34 a-b are configured to evaluate bandwidth parameters(inclusive of bit rate, quality of service (QoS), uplink capacities andtolerances, backhaul characteristics, etc.) in accommodating and/ordowngrading (and possibly upgrading) requests from UE 20. In addition,communication system 10 can offer an optimum scheme for self-limitinglong term evolution (LTE) configurations, femto architectures, andvarious other network topologies, which can be managed according totheir current link limitations (e.g., involving backhaul 12).

In more practical terms, a majority of network traffic congestion canoccur due to non-RTP/RTP control protocol (RTCP) flows, or at leastflows that are not visible to the transport network. The objective is tomatch uplink radio access bearer (RAB) parameters to the availableuplink bandwidth, without affecting existing client functions. Femto isa particular use case, where the RAB capacity commonly exceeds theuplink bandwidth. Given that the bandwidth can be limited on the accesslink, communication system 10 can offer the use case of a single femtoon a single access link. In other scenarios (potentially, less likely),multiple femtos can share a single access link. In an enterprisescenario, a single enterprise controller can be available and, hence,the aggregated bandwidth can be sensed. A local radio resourcemanagement functionality can use this sensed bandwidth to optimallyallocate bandwidth amongst the femtos in a particular enterpriseconfiguration. In one particular example, base station 30 receives theuplink request, evaluates bandwidth parameters, and subsequentlyauthorizes, or downgrades the request from UE 20. In a macro networkexample, the same activities can be completed by MME 56, by an SGSN, orby any other element, or by any suitable combination of various networkelements.

Consider another example flow in which UE 20 requests a particular radioaccess bearer configuration. In this particular example, UE 20 hasrequested an uplink channel, accompanied by a bit rate to be supported.Prior to even receiving this request, base station 30 can continuouslymonitor its uplink. It should be noted that base station 30 can includeintelligence to determine how frequently bandwidth uplink bandwidthshould be measured. In this particular example, UE 20 requests a 1MB/second bit rate on the uplink; however, base station 30 has theintelligence to identify it is operating on one end of a DSL link. Inthis particular example, base station 30 modifies this request such thatwhen the request propagates through the network, it has been adjusted toaccount for practical considerations of the current bandwidth for thelink. For example, the request is seen by the network in its downgradedformat, for example, from a requested 1 MB/second bit rate to a morereasonable 300 KB/second bit rate. This downgraded signaling can flowthrough the network, where a chain of negotiations in the control planetraverses back toward UE 20, which ultimately receives a 300 KB/seconduplink speed.

Separately, communication system 10 can also accommodate communicationsinvolving local IP network 28. Hence, there is enhanced intelligence inbase station 30 and/or network element 42 in defining where flows shouldbe routed. In situations where base station 30 has a local IP access(LIPA) functionality, base station 30 can determine which flows shouldpropagate over local IP network 28 and/or backhaul network 12. Thus,base station 30 has the ability to breakout local flows involving UE 20.Consider a use case for a femto cell in which an individual would liketo access his photos, music, etc., which may be provided in media server#1 60. Packets associated with these activities do not have to extendout to the service network and, instead, can be routed directly throughlocal IP network 28. In one particular example, base station 30 canterminate flows for UE 20 and also provide network address translation(NAT) for such flows (e.g., between the IP address allocated by packetgateway 40 and the IP address of local IP network 28). More specificoperations are best understood via one or more additional examples thatare offered below with reference to FIGS. 2-4. Before turning to some ofthe operations of this architecture, a brief discussion is providedabout some of the infrastructure of FIG. 1.

UE 20 can be associated with clients, customers, or end users wishing toinitiate a communication in communication system 10 via some network.The term ‘user equipment’ is inclusive of devices used to initiate acommunication, such as a computer, a personal digital assistant (PDA), alaptop or electronic notebook, a cellular telephone, an iPhone, an IPphone, or any other device, component, element, or object capable ofinitiating voice, audio, video, media, or data exchanges withincommunication system 10. UE 20 may also be inclusive of a suitableinterface to the human user, such as a microphone, a display, or akeyboard or other terminal equipment. UE 20 may also be any device thatseeks to initiate a communication on behalf of another entity orelement, such as a program, a database, or any other component, device,element, or object capable of initiating an exchange withincommunication system 10. Data, as used herein in this document, refersto any type of numeric, voice, video, media, or script data, or any typeof source or object code, or any other suitable information in anyappropriate format that may be communicated from one point to another.On power up, UE 20 can be configured to initiate a request for aconnection with a service provider. A user agreement can beauthenticated by the service provider based on various service providercredentials (e.g., subscriber identity module (SIM), Universal SIM(USIM), certifications, etc.). More specifically, a device can beauthenticated by the service provider using some predetermined financialrelationship.

Base station 30 can include base station switch 26, along with anyappropriate transceivers and/or controllers to assist in its operations.The communications interface provided by the radio access network (e.g.,of a Node B) may allow data to be exchanged between UE 20 and any numberof selected elements within communication system 10. Base station 30 mayfacilitate the delivery of a request packet generated by UE 20 and,further, the reception of information sought by an end user. Basestation 30 is only one example of a communications interface between UE20 and the service network. Other suitable types of communicationsinterfaces may be used for any appropriate network design and, further,be based on specific communications architectures.

In one particular example, base station 30 is a femto access point(i.e., a femto base station), which represents a small cellular basestation designed for use in residential or business environments. Thefemto access point can connect to the service provider's network viabroadband (such as DSL, WiMAX, WiFi, cable, etc.) in one example. Thefemto access point can offer an access point base station, and supportmultiple active mobile nodes in a given setting (e.g., business,residential, etc.). In one example implementation, the femto accesspoint communicates with UE 20 over a radio interface using licensedspectrum and, further, connects to the mobile network infrastructureover a fixed broadband connection. The femto cell can allow a serviceprovider to extend service coverage indoors, especially where accesswould otherwise be limited or unavailable. The femto cell canincorporate the functionality of a typical base station, but extend itto allow a simpler, self-contained deployment. An example implementationof the femto access point is a Universal Mobile TelecommunicationsSystem (UMTS) femto cell containing a Node B and components of a radionetwork controller (RNC) and Ethernet for the backhaul. The conceptspresented herein are applicable to all standards, including GSM, codedivision multiple access (CDMA) 2000, WCDMA, Time Division SynchronousCDMA, WiMAX, LTE, etc.

Packet gateway 40 is a packet data node (PDN) gateway that providesconnectivity from UE 20 to external packet data networks by being thepoint of exit and entry of traffic for UE 20. UE 20 may havesimultaneous connectivity with more than one packet gateway 40 foraccessing multiple PDNs. Packet gateway 40 can perform policyenforcement, packet filtering, charging support, lawful interception ofmessages and signaling, packet screening, etc. Packet gateway 40 canalso act as the anchor for mobility between 3 GPP and non-3 GPPtechnologies such as WiMAX and 3 GPP2.

Network element 42 and base station 30 are devices configured tofacilitate service flows between endpoints and a given network (e.g.,for networks such as those illustrated in FIG. 1). As used herein inthis Specification, the term ‘network element’ is meant to encompassboth of these devices and, further, could be in the form of routers,switches, gateways, bridges, loadbalancers, firewalls, servers,processors, controllers, network nodes, modules, or any other suitabledevice, component, element, or object operable to exchange informationin a network environment. The network elements may include bandwidthsensing modules 34 a-b to support the activities associated withbandwidth management, as outlined herein. Moreover, the network elementsmay include any suitable hardware, software, components, modules,interfaces, or objects that facilitate the operations thereof. This maybe inclusive of appropriate algorithms and communication protocols thatallow for the effective exchange of data or information.

In one implementation, network element 42 and/or base station 30 caninclude software (e.g., bandwidth sensing modules 34 a-b) to achieve orto foster the bandwidth sensing operations, as outlined herein in thisdocument. Note that in one example, base station 30 includes basestation switch 28, which can have an internal structure (e.g., with aprocessor, a memory element, etc.) to facilitate some of the operationsdescribed herein. This internal structure may be provided in otherinternal elements within base station 30. In other embodiments, all ofthese bandwidth-sensing features may be provided externally to theseelements or included in some other network element to achieve thisintended functionality. Alternatively, network element 42 and basestation 30 include this software (or reciprocating software) that cancoordinate with each other in order to achieve the bandwidth managementoperations, as outlined herein. In still other embodiments, one or bothof these devices may include any suitable algorithms, hardware,software, components, modules, interfaces, or objects that facilitatethe operations thereof.

In operation, network element 42 can provide access gateway functionsbetween (for example) a wireless domain and an IP network. In exampleembodiments, it can be the first hop IP router from the user'sperspective and, further, provide network access server (NAS) andaccounting client capabilities for interaction with an authentication,authorization, and accounting (AAA) servers. Network element 42 can alsosupport access network authentication and security functions. Networkelement 42 can also provide local mobility anchor capability so thatusers can move between base stations. Network element 42 can also cacheauthentication and security information to accommodate a fast roaming ofusers across base stations, or between gateways, and network element 42.Network element 42 can provide the termination of a mobility functionacross base stations and the foreign agent function. Network element 42can also map the radio bearer to the IP network. Additionally, it canact as an IP gateway for the IP host function that is located on thecorresponding base station. In certain examples, network element 42 canoffer IP functions performed for the access network including end-to-endquality of service, mobility, and security.

Note that, depending on the network, there may be difficulties with thedelay between the reporting of a need to adjust the aggregate maximumbit rate (AMBR)/guaranteed bit rate (GBR) and the actual conditions atthe point when the adjustment is ultimately applied. In some instances,bandwidth constraints may have improved. Thus, communication system 10(e.g., through network element 42 and/or base station 30) can offer amechanism for upgrading bandwidth allocations. Sensing of the bandwidthcan be performed repeatedly, with a defined periodicity, where theseactivities can be used in conjunction with reversing previous downgradedecisions.

A given Node B (e.g., in femto architectures) can use radio measurementsto provide an enhanced resource allocation functionality. The reportingin this case can be performed by the transport network. Node Bs can havea measurement capability both locally and remotely (for UE 20) and,further, perform resource allocation that considers these measurements.Communication system 10 can use bandwidth measurements both locally(e.g., at a Node B) and remotely (e.g., via network element 42 or asecurity gateway or a home Node B (HNB) gateway) together with flowdestinations (e.g., selective IP traffic offloading (SIPTO), non-SIPTO)to perform resource allocations. Hence, communication system 10 canprovide the dynamic data needed to characterize backhaul 12 and,further, constrain actual data use within the limits that are present.

In one particular example involving a femto cell, IP addresses can beseen by the femto cell, where the femto cell has an understanding of thehome network addressing. The femto cell can measure traffic on a givenlink and identify circumstances tending to suggest that traffic iscoming from the service network. Along similar reasoning, the femto cellcan also identify when traffic is propagating to local IP network 28.Thus, the local traffic and tunneled traffic can traverse the sameunderlying radio link and physical media path until they split along thephysical path. In a generic sense, and with reference to particularlinks in the GTP architecture, communication system 10 can effectivelycreate a data tunnel within a data tunnel. Continuing along with thisanalogy, the GTP tunnel can be viewed as the inner tunnel, where thebandwidth allocated by a backhaul provider (e.g., cable) to a femto cellcan be viewed as the outer tunnel. Local traffic can flow outside a GTPtunnel, but still inside the bandwidth tunnel. In using bandwidthsensing modules 34 a-b, the outer tunnel may change size dynamically,while the inner tunnel size can be controlled by GTP extensions. Theinner tunnel may require adjustments to remain smaller than the outertunnel. These adjustments may also leave room for a certain amount oflocal traffic. In one example, the IP address assigned to the GTP tunnelcan be farther into the wireless network system, while the IP addressfor the local traffic can point to a link closer to the femto cell.

Returning to the infrastructure of FIG. 1, in general terms, servinggateway 54 is associated with an SGSN user plane in an IP network. Inother instances, serving gateway 54 could be an IP-enabled RNC. Servinggateway 54 can be configured to route and to forward user data packets,while also acting as the mobility anchor for the user plane duringinter-Node B handovers. Serving gateway 54 can act as the anchor formobility between LTE and other 3 GPP technologies (i.e., terminating theS4 interface and relaying the traffic between 2 G/3 G systems and packetgateway 40). For idle-state UEs, serving gateway 54 can terminate thedata path and trigger paging when data arrives for UE 20. Servinggateway 54 can also manage and store UE contexts (e.g., parameters ofthe IP bearer service, network internal routing information, etc.).

MME 56 can be configured to operate as a control node for the LTEaccess-network. It further can be responsible for idle mode UE trackingand paging procedures (e.g., including retransmissions). Furthermore,MME 56 can be involved in the bearer activation/deactivation process andcan be responsible for choosing serving gateway 54 for UE 20 at theinitial attach (and at time of an intra-LTE handover involving corenetwork node relocation). MME 56 can also be responsible forauthenticating the user. MME 56 also provides the control plane functionfor mobility between LTE and 2 G/3 G access networks with the S3interface, terminating at MME 56 from an SGSN.

In regard to particular applications involving UE 20, media server #1 60and media server #2 50 can represent one or more video servers, whichcan provide streaming video to an individual associated with UE 20. Forexample, an individual could be uploading (or streaming) video over thenetwork to which UE 20 is connected. This could involve technologiessuch as flip video, webcams, YouTube, and various other videotechnologies involving any type of uploading and/or streaming videodata.

FIG. 2 is a simplified flow diagram 60 illustrating one exampleimplementation associated with communication system 10. This particularexample involves a femto cell, which can be part of a femto base stationthat serves the same functionalities as those described above withrespect to base station 30. In this particular example, as shown in stepone, a link characterization occurs between base station 30 and networkelement 42. This could involve bandwidth sensing modules 34 a-b, whichcan systematically identify bandwidth parameters associated with one ormore links. At step two, NAS signaling requests a specific bit rate.This request is intercepted by the femto cell, where the request isappropriately downgraded according to the link characterization. At stepthree, typical data transmission procedures/negotiations/signaling canoccur between UE 20 and MME 56. At step four, end-to-end (E2E)communications can occur involving UE 20 and one or more networks. Notethat these communications are defined by the downgrade that occurredpreviously in step two.

In typical configurations, an LTE femto cell architecture can have a GTPtunnel between a femto cell and a security gateway (Se-GW)/servinggateway (SGW) 54. If the backhaul is congested, the AMBR limits inpacket gateway 40 can be insufficient. Packets can be systematicallydropped over the backhaul network, leading to degrading conditions thatinhibit a quality experience for individuals operating UE 20. A givenfemto cell is configured to negotiate the use of proprietary GTP headersbetween the femto cell and the SeGW/serving gateway 54. The headerextensions can include sequence numbers, an average transmission orreceiving rates sent over serving gateway 54 to the femto interface, apacket reception error rate, negotiated AMBR/guaranteed bit rate (GBR)values, or any other appropriate parameter are characteristic that maybe provided via header extensions.

Network element 42 can use header extensions to identify that anoriginal bit rate request (for example, 2 MB/second) was made; however,the average uplink throughput is actually 250 KB/second. A given femtocell can identify how many packets are sent into the network and,further, it can receive information from network element 42 indicatingthat network element 42 is only receiving a fraction of the originallyrequested rate. Therefore, an inference can be made that packets arebeing dropped such that a renegotiation of the bit rate should beexecuted.

Rate averaging can allow network element 42 to provide a device (e.g.,residing at the far end of the link) with sending and receiving averagesvalues (e.g., over the last minute, the last hour, the last day, etc.).A given femto cell can be configured to determine instantaneous backhaulbandwidth. In regards to the local IP access activities, a given femtocell can be configured to determine what percentage of the RAB bandwidthis being backhauled over the S1-U interface (e.g., compared to flowsthat may be routed locally over local IP network 28). Furthermore, thefemto cell can be configured to indicate to the mobile if the GBR/AMBRcannot be sustained due to backhaul bandwidth. Additionally, theSeGW/serving gateway 54 can be configured to determine if the backhaulbandwidth can sustain the AMBR/GBR signaled by the femto cell. If thebit rate cannot be sustained, the SeGW/serving gateway 54 is operable toindicate to MME 56 that a packet data protocol (PDP) contextmodification should occur with a downgrade in the AMBR/GBR in order toenable a successful transmission over backhaul network 12. The downgradecan involve QoS, the radio accessed bearer, or any other suitable linkparameter.

Turning to FIG. 3, FIG. 3 is a simplified flow diagram 70 illustratinganother example associated with communication system 10. At step one, alink characterization occurs between base station 30 and network element42. At step two, and interface between network element 42 and MME 56passes information associated with this particular link. At step three,NAS signaling is used to request a given bit rate. This request isterminated by MME 56, where the request is appropriately downgradedaccording to the link characterization of step one. At step four,typical data transmission procedures/negotiations/signaling can occurbetween UE 20 and packet gateway 40. At step five, end-to-endcommunications occur involving UE 20 and one or more networks, wheresuch communications have links defined by the downgrade that occurredpreviously.

FIG. 4 is a simplified flow diagram 80 illustrating another exampleassociated with communication system 10. In step one, a linkcharacterization occurs, where this signaling includes interactionsbetween base station 30 and network element 42. This particularsignaling offers an indication of a local gateway (L-GW) option for thisspecific request. Network element 42 and MME 56 interact at step two,where MME 56 passes information indicating that the L-GW is active. Atstep three, NAS signaling requests a given bit rate, which is terminatedby MME 56. This particular request is not downgraded because of the L-GWoption. At step four, typical data transmissionprocedures/negotiations/signaling can occur between UE 20 and packetgateway 40. At step five, an end-to-end flow is established for UE 20and packet gateway 40. At step six, a congestion indication is exchangedbetween MME 56 and network element 42. At step seven, a downgrade forQoS signaling occurs between base station 30 and MME 56. At step eight,end-to-end communications occur involving UE 20 and packet gateway 40,where such communications have links defined by the downgrade thatoccurred previously.

Note that in certain example implementations, the bandwidth sensingand/or downgrading functions outlined herein may be implemented by logicencoded in one or more tangible media (e.g., embedded logic provided inan application specific integrated circuit [ASIC], digital signalprocessor [DSP] instructions, software [potentially inclusive of objectcode and source code] to be executed by a processor, or other similarmachine, etc.). In some of these instances, a memory element [as shownin FIG. 1] can store data used for the operations described herein. Thisincludes the memory element being able to store software, logic, code,or processor instructions that are executed to carry out the activitiesdescribed in this Specification. A processor can execute any type ofinstructions associated with the data to achieve the operations detailedherein in this Specification. In one example, the processor [as shown inFIG. 1] could transform an element or an article (e.g., data) from onestate or thing to another state or thing. In another example, theactivities outlined herein may be implemented with fixed logic orprogrammable logic (e.g., software/computer instructions executed by aprocessor) and the elements identified herein could be some type of aprogrammable processor, programmable digital logic (e.g., a fieldprogrammable gate array [FPGA], an erasable programmable read onlymemory (EPROM), an electrically erasable programmable ROM (EEPROM)) oran ASIC that includes digital logic, software, code, electronicinstructions, or any suitable combination thereof.

In one example implementation, network element 42 and/or base station 30include software in order to achieve the bandwidth sensing and/ordowngrading functions outlined herein. These activities can befacilitated by bandwidth sensing modules 34 a-b. Both network element 42and/or base station 30 can include memory elements for storinginformation to be used in achieving the bandwidth sensing and/ordowngrading operations as outlined herein. Additionally, each of thesedevices may include a processor that can execute software or analgorithm to perform the bandwidth sensing and/or downgrading activitiesas discussed in this Specification. These devices may further keepinformation in any suitable memory element [random access memory (RAM),ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any othersuitable component, device, element, or object where appropriate andbased on particular needs. Any of the memory items discussed hereinshould be construed as being encompassed within the broad term ‘memoryelement.’ Similarly, any of the potential processing elements, modules,and machines described in this Specification should be construed asbeing encompassed within the broad term ‘processor.’ Each of the networkelements can also include suitable interfaces for receiving,transmitting, and/or otherwise communicating data or information in anetwork environment.

Note that with the example provided above, as well as numerous otherexamples provided herein, interaction may be described in terms of two,three, or four network elements. However, this has been done forpurposes of clarity and example only. In certain cases, it may be easierto describe one or more of the functionalities of a given set of flowsby only referencing a limited number of network elements. It should beappreciated that communication system 10 (and its teachings) are readilyscalable and can accommodate a large number of components, as well asmore complicated/sophisticated arrangements and configurations.Accordingly, the examples provided should not limit the scope or inhibitthe broad teachings of communication system 10 as potentially applied toa myriad of other architectures.

It is also important to note that the steps in the preceding flowdiagrams illustrate only some of the possible signaling scenarios andpatterns that may be executed by, or within, communication system 10.Some of these steps may be deleted or removed where appropriate, orthese steps may be modified or changed considerably without departingfrom the scope of the present disclosure. In addition, a number of theseoperations have been described as being executed concurrently with, orin parallel to, one or more additional operations. However, the timingof these operations may be altered considerably. The precedingoperational flows have been offered for purposes of example anddiscussion. Substantial flexibility is provided by communication system10 in that any suitable arrangements, chronologies, configurations, andtiming mechanisms may be provided without departing from the teachingsof the present disclosure.

In a separate endeavor, communication system 10 can generally beconfigured or arranged to represent the LTE architecture, the 3 Garchitecture applicable to UMTS environments, or any suitable networkingsystem or arrangement that provides a communicative platform forcommunication system 10. In other examples, FIG. 1 could readily includean SGSN, a gateway GPRS support node (GGSN), any type of network accessserver, network node, etc. Moreover, the present disclosure is equallyapplicable to other cellular and/or wireless technology including CDMA,Wi-Fi, WiMax, etc.

Although the present disclosure has been described in detail withreference to particular arrangements and configurations, these exampleconfigurations and arrangements may be changed significantly withoutdeparting from the scope of the present disclosure. For example,although the present disclosure has been described with reference toparticular communication exchanges involving certain backhaul links,AAA, and authentication protocols, communication system 10 may beapplicable to other exchanges, routing protocols, authenticationprotocols, or routed protocols in which packets (not necessarily therouting protocol/packets described) are exchanged in order to providebandwidth sensing (and subsequent adjustment) activities. In addition,other example environments that could use the features defined hereininclude Pico architectures, where an appropriate bandwidth sensing (andpossible bandwidth adjustment for associated links) could occur for UE20.

1. A method, comprising: identifying a bandwidth parameter associatedwith a network link; evaluating a bandwidth request associated with userequipment, wherein the bandwidth request is associated with a session,which involves the user equipment and which implicates the network link;and modifying the bandwidth request based on the bandwidth parameterthat was identified.
 2. The method of claim 1, wherein one or moreheader extensions in one or more packets are evaluated in order toassist in identifying the bandwidth parameter, and wherein the one ormore header extensions include a selected one of packet sequencenumbers, an average packet transmission rate, an average packetreceiving rate, and a packet reception error rate.
 3. The method ofclaim 2, wherein modifying the bandwidth request includes downgradingthe bandwidth request to lower a bit rate based on the bandwidthparameter identified for the network link.
 4. The method of claim 3,wherein the bandwidth parameter associated with the network link issubsequently evaluated in order to reverse the downgrading of thebandwidth request.
 5. The method of claim 2, wherein one or more of theheader extensions include negotiated aggregate maximum bit rate(AMBR)/guaranteed bit rate (GBR) values.
 6. The method of claim 5,further comprising: identifying that the AMBR/GBR value cannot besustained due to the bandwidth parameter; and communicating to amobility management entity (MME) that a packet data protocol (PDP)context modification should occur for downgrading the network link. 7.The method of claim 1, further comprising: identifying a local gateway(L-GW) option for a subsequent request; and determining not to downgradethe network link based on the L-GW option being present.
 8. Logicencoded in one or more tangible media that includes code for executionand when executed by a processor operable to perform operationscomprising: identifying a bandwidth parameter associated with a networklink; evaluating a bandwidth request associated with user equipment,wherein the bandwidth request is associated with a session, whichinvolves the user equipment and which implicates the network link; andmodifying the bandwidth request based on the bandwidth parameter thatwas identified.
 9. The logic of claim 8, wherein one or more headerextensions in one or more packets are evaluated in order to assist inidentifying the bandwidth parameter, and wherein the one or more headerextensions include a selected one of packet sequence numbers, an averagepacket transmission rate, an average packet receiving rate, and a packetreception error rate.
 10. The logic of claim 9, wherein one or more ofthe header extensions include negotiated aggregate maximum bit rate(AMBR)/guaranteed bit rate (GBR) values.
 11. The logic of claim 9, beingfurther operable to perform operations comprising: identifying that theAMBR/GBR value cannot be sustained due to the bandwidth parameter; andcommunicating to a mobility management entity (MME) that a packet dataprotocol (PDP) context modification should occur for downgrading thenetwork link.
 12. The logic of claim 8, wherein the bandwidth parameterassociated with the network link is subsequently evaluated in order toreverse a downgrading of the bandwidth request.
 13. The logic of claim8, being further operable to perform operations comprising: identifyinga local gateway (L-GW) option for a subsequent request; and determiningnot to downgrade the network link based on the L-GW option beingpresent.
 14. An apparatus, comprising: a memory element configured tostore data, a processor operable to execute instructions associated withthe data, and a bandwidth sensing module configured to: identify abandwidth parameter associated with a network link; evaluate a bandwidthrequest associated with user equipment, wherein the bandwidth request isassociated with a session, which involves the user equipment and whichimplicates the network link; and modify the bandwidth request based onthe bandwidth parameter that was identified.
 15. The apparatus of claim14, wherein one or more header extensions in one or more packets areevaluated in order to assist in identifying the bandwidth parameter, andwherein the one or more header extensions include a selected one ofpacket sequence numbers, an average packet transmission rate, an averagepacket receiving rate, and a packet reception error rate.
 16. Theapparatus of claim 15, wherein modifying the bandwidth request includesdowngrading the bandwidth request to lower a bit rate based on thebandwidth parameter identified for the network link.
 17. The apparatusof claim 16, wherein the bandwidth parameter associated with the networklink is subsequently evaluated in order to reverse the downgrading ofthe bandwidth request.
 18. The apparatus of claim 15, wherein one ormore of the header extensions include negotiated aggregate maximum bitrate (AMBR)/guaranteed bit rate (GBR) values.
 19. The apparatus of claim18, wherein the bandwidth sensing module is further configured to:identify that the AMBR/GBR value cannot be sustained due to thebandwidth parameter; and communicate to a mobility management entity(MME) that a packet data protocol (PDP) context modification shouldoccur for downgrading the network link.
 20. The apparatus of claim 14,wherein the bandwidth sensing module is further configured to: identifya local gateway (L-GW) option for a subsequent request; and determinenot to downgrade the network link based on the L-GW option beingpresent.